dmesg - Intel Xeon E5-2682 v4
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 4.4.0-63-generic (buildd@lgw01-03) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #84~14.04.2-Ubuntu SMP Mon Feb 13 11:04:58 UTC 2017 (Ubuntu 4.4.0-63.84~14.04.2-generic 4.4.44)
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
x86/fpu: Using 'eager' FPU context switches.
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x00000000bffdffff] usable
BIOS-e820: [mem 0x00000000bffe0000-0x00000000bfffffff] reserved
BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000023fffffff] usable
NX (Execute Disable) protection: active
SMBIOS 2.8 present.
DMI: Alibaba Cloud Alibaba Cloud ECS, BIOS rel-1.7.5-0-ge51488c-20140602_164612-nilsson.home.kraxel.org 04/01/2014
Hypervisor detected: KVM
e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
e820: last_pfn = 0x240000 max_arch_pfn = 0x400000000
MTRR default type: write-back
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-FFFFF write-protect
MTRR variable ranges enabled:
0 base 0000C0000000 mask 3FFFC0000000 uncachable
1 disabled
2 disabled
3 disabled
4 disabled
5 disabled
6 disabled
7 disabled
x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT
e820: last_pfn = 0xbffe0 max_arch_pfn = 0x400000000
found SMP MP-table at [mem 0x000f0e80-0x000f0e8f] mapped at [ffff8800000f0e80]
Scanning 1 areas for low memory corruption
Base memory trampoline at [ffff880000099000] 99000 size 24576
Using GB pages for direct mapping
BRK [0x02210000, 0x02210fff] PGTABLE
BRK [0x02211000, 0x02211fff] PGTABLE
BRK [0x02212000, 0x02212fff] PGTABLE
RAMDISK: [mem 0x35528000-0x36a8bfff]
ACPI: Early table checksum verification disabled
ACPI: RSDP 0x00000000000F0C20 000014 (v00 BOCHS )
ACPI: RSDT 0x00000000BFFE1972 000030 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)
ACPI: FACP 0x00000000BFFE0B52 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)
ACPI: DSDT 0x00000000BFFE0040 000B12 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001)
ACPI: FACS 0x00000000BFFE0000 000040
ACPI: SSDT 0x00000000BFFE0BC6 000D1C (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001)
ACPI: APIC 0x00000000BFFE18E2 000090 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001)
ACPI: Local APIC address 0xfee00000
No NUMA configuration found
Faking a node at [mem 0x0000000000000000-0x000000023fffffff]
NODE_DATA(0) allocated [mem 0x23fff9000-0x23fffdfff]
kvm-clock: Using msrs 4b564d01 and 4b564d00
kvm-clock: cpu 0, msr 2:3fff1001, primary cpu clock
kvm-clock: using sched offset of 2317023288 cycles
clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
Zone ranges:
DMA [mem 0x0000000000001000-0x0000000000ffffff]
DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
Normal [mem 0x0000000100000000-0x000000023fffffff]
Device empty
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x0000000000001000-0x000000000009efff]
node 0: [mem 0x0000000000100000-0x00000000bffdffff]
node 0: [mem 0x0000000100000000-0x000000023fffffff]
Initmem setup node 0 [mem 0x0000000000001000-0x000000023fffffff]
On node 0 totalpages: 2097022
DMA zone: 64 pages used for memmap
DMA zone: 21 pages reserved
DMA zone: 3998 pages, LIFO batch:0
DMA32 zone: 12224 pages used for memmap
DMA32 zone: 782304 pages, LIFO batch:31
Normal zone: 20480 pages used for memmap
Normal zone: 1310720 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x608
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ5 used by override.
ACPI: IRQ9 used by override.
ACPI: IRQ10 used by override.
ACPI: IRQ11 used by override.
Using ACPI (MADT) for SMP configuration information
smpboot: Allowing 4 CPUs, 0 hotplug CPUs
PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
PM: Registered nosave memory: [mem 0xbffe0000-0xbfffffff]
PM: Registered nosave memory: [mem 0xc0000000-0xfeffbfff]
PM: Registered nosave memory: [mem 0xfeffc000-0xfeffffff]
PM: Registered nosave memory: [mem 0xff000000-0xfffbffff]
PM: Registered nosave memory: [mem 0xfffc0000-0xffffffff]
e820: [mem 0xc0000000-0xfeffbfff] available for PCI devices
Booting paravirtualized kernel on KVM
clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 34 pages/cpu @ffff88023fc00000 s98328 r8192 d32744 u524288
pcpu-alloc: s98328 r8192 d32744 u524288 alloc=1*2097152
pcpu-alloc: [0] 0 1 2 3
KVM setup async PF for cpu 0
kvm-stealtime: cpu 0, msr 23fc0da00
PV qspinlock hash table entries: 256 (order: 0, 4096 bytes)
Built 1 zonelists in Node order, mobility grouping on. Total pages: 2064233
Policy zone: Normal
PID hash table entries: 4096 (order: 3, 32768 bytes)
Calgary: detecting Calgary via BIOS EBDA area
Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Memory: 8149600K/8388088K available (8242K kernel code, 1302K rwdata, 3996K rodata, 1496K init, 1316K bss, 238488K reserved, 0K cma-reserved)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 64.
RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=4.
RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
NR_IRQS:33024 nr_irqs:456 16
Console: colour dummy device 80x25
console [tty0] enabled
tsc: Detected 2494.222 MHz processor
Calibrating delay loop (skipped) preset value.. 4988.44 BogoMIPS (lpj=9976888)
pid_max: default: 32768 minimum: 301
ACPI: Core revision 20150930
ACPI: 2 ACPI AML tables successfully acquired and loaded
Security Framework initialized
Yama: becoming mindful.
AppArmor: AppArmor initialized
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Initializing cgroup subsys io
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys perf_event
Initializing cgroup subsys net_prio
Initializing cgroup subsys hugetlb
Initializing cgroup subsys pids
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 10 MCE banks
Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
Freeing SMP alternatives memory: 32K (ffffffff820bd000 - ffffffff820c5000)
ftrace: allocating 32160 entries in 126 pages
smpboot: APIC(0) Converting physical 0 to logical package 0
smpboot: Max logical packages: 1
x2apic enabled
Switched APIC routing to physical x2apic.
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
TSC deadline timer enabled
smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2682 v4 @ 2.50GHz (family: 0x6, model: 0x4f, stepping: 0x1)
Performance Events: unsupported p6 CPU model 79 no PMU driver, software events only.
KVM setup paravirtual spinlock
x86: Booting SMP configuration:
.... node #0, CPUs: #1
kvm-clock: cpu 1, msr 2:3fff1041, secondary cpu clock
KVM setup async PF for cpu 1
kvm-stealtime: cpu 1, msr 23fc8da00
#2
kvm-clock: cpu 2, msr 2:3fff1081, secondary cpu clock
KVM setup async PF for cpu 2
kvm-stealtime: cpu 2, msr 23fd0da00
#3
kvm-clock: cpu 3, msr 2:3fff10c1, secondary cpu clock
x86: Booted up 1 node, 4 CPUs
smpboot: Total of 4 processors activated (19953.77 BogoMIPS)
KVM setup async PF for cpu 3
kvm-stealtime: cpu 3, msr 23fd8da00
devtmpfs: initialized
evm: security.selinux
evm: security.SMACK64
evm: security.SMACK64EXEC
evm: security.SMACK64TRANSMUTE
evm: security.SMACK64MMAP
evm: security.ima
evm: security.capability
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
pinctrl core: initialized pinctrl subsystem
RTC time: 8:49:31, date: 07/06/17
NET: Registered protocol family 16
cpuidle: using governor ladder
cpuidle: using governor menu
PCCT header not found.
ACPI: bus type PCI registered
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
PCI: Using configuration type 1 for base access
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
ACPI: Interpreter enabled
ACPI: (supports S0 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI]
acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
acpiphp: Slot [3] registered
acpiphp: Slot [4] registered
acpiphp: Slot [5] registered
acpiphp: Slot [6] registered
acpiphp: Slot [7] registered
acpiphp: Slot [8] registered
acpiphp: Slot [9] registered
acpiphp: Slot [10] registered
acpiphp: Slot [11] registered
acpiphp: Slot [12] registered
acpiphp: Slot [13] registered
acpiphp: Slot [14] registered
acpiphp: Slot [15] registered
acpiphp: Slot [16] registered
acpiphp: Slot [17] registered
acpiphp: Slot [18] registered
acpiphp: Slot [19] registered
acpiphp: Slot [20] registered
acpiphp: Slot [21] registered
acpiphp: Slot [22] registered
acpiphp: Slot [23] registered
acpiphp: Slot [24] registered
acpiphp: Slot [25] registered
acpiphp: Slot [26] registered
acpiphp: Slot [27] registered
acpiphp: Slot [28] registered
acpiphp: Slot [29] registered
acpiphp: Slot [30] registered
acpiphp: Slot [31] registered
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
pci_bus 0000:00: root bus resource [io 0x0d00-0xadff window]
pci_bus 0000:00: root bus resource [io 0xae0f-0xaeff window]
pci_bus 0000:00: root bus resource [io 0xaf20-0xafdf window]
pci_bus 0000:00: root bus resource [io 0xafe4-0xffff window]
pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
pci 0000:00:01.1: reg 0x20: [io 0xc0e0-0xc0ef]
pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
pci 0000:00:01.2: [8086:7020] type 00 class 0x0c0300
pci 0000:00:01.2: reg 0x20: [io 0xc040-0xc05f]
pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
pci 0000:00:01.3: quirk: [io 0x0600-0x063f] claimed by PIIX4 ACPI
pci 0000:00:01.3: quirk: [io 0x0700-0x070f] claimed by PIIX4 SMB
pci 0000:00:02.0: [1013:00b8] type 00 class 0x030000
pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref]
pci 0000:00:02.0: reg 0x14: [mem 0xfebd0000-0xfebd0fff]
pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref]
pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000
pci 0000:00:03.0: reg 0x10: [io 0xc060-0xc07f]
pci 0000:00:03.0: reg 0x14: [mem 0xfebd1000-0xfebd1fff]
pci 0000:00:03.0: reg 0x30: [mem 0xfeb80000-0xfebbffff pref]
pci 0000:00:04.0: [1af4:1003] type 00 class 0x078000
pci 0000:00:04.0: reg 0x10: [io 0xc080-0xc09f]
pci 0000:00:04.0: reg 0x14: [mem 0xfebd2000-0xfebd2fff]
pci 0000:00:05.0: [1af4:1001] type 00 class 0x010000
pci 0000:00:05.0: reg 0x10: [io 0xc000-0xc03f]
pci 0000:00:05.0: reg 0x14: [mem 0xfebd3000-0xfebd3fff]
pci 0000:00:06.0: [1af4:1002] type 00 class 0x00ff00
pci 0000:00:06.0: reg 0x10: [io 0xc0a0-0xc0bf]
pci 0000:00:07.0: [1af4:1014] type 00 class 0x00ff00
pci 0000:00:07.0: reg 0x10: [io 0xc0c0-0xc0df]
ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
ACPI: PCI Interrupt Link [LNKS] (IRQs *9)
ACPI: Enabled 16 GPEs in block 00 to 0F
vgaarb: setting as boot device: PCI:0000:00:02.0
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:00:02.0
SCSI subsystem initialized
libata version 3.00 loaded.
ACPI: bus type USB registered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
e820: reserve RAM buffer [mem 0xbffe0000-0xbfffffff]
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
amd_nb: Cannot enumerate AMD northbridges
clocksource: Switched to clocksource kvm-clock
AppArmor: AppArmor Filesystem Enabled
pnp: PnP ACPI init
pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:01: Plug and Play ACPI device, IDs PNP0303 (active)
pnp 00:02: Plug and Play ACPI device, IDs PNP0f13 (active)
pnp 00:03: [dma 2]
pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active)
pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
pnp: PnP ACPI: found 5 devices
clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
pci_bus 0000:00: resource 5 [io 0x0d00-0xadff window]
pci_bus 0000:00: resource 6 [io 0xae0f-0xaeff window]
pci_bus 0000:00: resource 7 [io 0xaf20-0xafdf window]
pci_bus 0000:00: resource 8 [io 0xafe4-0xffff window]
pci_bus 0000:00: resource 9 [mem 0x000a0000-0x000bffff window]
pci_bus 0000:00: resource 10 [mem 0xc0000000-0xfebfffff window]
NET: Registered protocol family 2
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
UDP hash table entries: 4096 (order: 5, 131072 bytes)
UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
NET: Registered protocol family 1
pci 0000:00:00.0: Limiting direct PCI/PCI transfers
pci 0000:00:01.0: PIIX3: Enabling Passive Release
pci 0000:00:01.0: Activating ISA DMA hang workarounds
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
pci 0000:00:02.0: Video device with shadowed ROM
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 21904K (ffff880035528000 - ffff880036a8c000)
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
software IO TLB [mem 0xbbfe0000-0xbffe0000] (64MB) mapped at [ffff8800bbfe0000-ffff8800bffdffff]
Scanning for low memory corruption every 60 seconds
futex hash table entries: 1024 (order: 4, 65536 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(1499302172.283:1): initialized
Initialise system trusted keyring
HugeTLB registered 1 GB page size, pre-allocated 0 pages
HugeTLB registered 2 MB page size, pre-allocated 0 pages
zbud: loaded
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
fuse init (API version 7.23)
Key type big_key registered
Allocating IMA MOK and blacklist keyrings.
Key type asymmetric registered
Asymmetric key parser 'x509' registered
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
efifb: probing for efifb
efifb: framebuffer at 0xfc000000, mapped to 0xffffc90001000000, using 1408k, total 1408k
efifb: mode is 800x600x24, linelength=2400, pages=1
efifb: scrolling: redraw
efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0
Console: switching to colour frame buffer device 100x37
fb0: EFI VGA frame buffer device
intel_idle: does not run on family 6 model 79
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
ACPI: Power Button [PWRF]
GHES: HEST is not enabled!
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
virtio-pci 0000:00:03.0: virtio_pci: leaving for legacy driver
virtio-pci 0000:00:04.0: virtio_pci: leaving for legacy driver
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
virtio-pci 0000:00:05.0: virtio_pci: leaving for legacy driver
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
virtio-pci 0000:00:06.0: virtio_pci: leaving for legacy driver
virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver
00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Linux agpgart interface v0.103
brd: module loaded
loop: module loaded
vda: vda1
ata_piix 0000:00:01.1: version 2.13
scsi host0: ata_piix
scsi host1: ata_piix
ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc0e0 irq 14
ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc0e8 irq 15
libphy: Fixed MDIO Bus: probed
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky
PPP generic driver version 2.4.2
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-platform: EHCI generic platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-platform: OHCI generic platform driver
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:01.2: UHCI Host Controller
uhci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:01.2: detected 2 ports
uhci_hcd 0000:00:01.2: irq 11, io base 0x0000c040
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 4.4.0-63-generic uhci_hcd
usb usb1: SerialNumber: 0000:00:01.2
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mousedev: PS/2 mouse device common for all mice
rtc_cmos 00:00: RTC can wake from S4
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
rtc_cmos 00:00: alarms up to one day, 114 bytes nvram
i2c /dev entries driver
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com
ledtrig-cpu: registered to indicate activity on CPUs
NET: Registered protocol family 10
NET: Registered protocol family 17
Key type dns_resolver registered
microcode: CPU0 sig=0x406f1, pf=0x1, revision=0x1
microcode: CPU1 sig=0x406f1, pf=0x1, revision=0x1
microcode: CPU2 sig=0x406f1, pf=0x1, revision=0x1
microcode: CPU3 sig=0x406f1, pf=0x1, revision=0x1
microcode: Microcode Update Driver: v2.01 , Peter Oruba
registered taskstats version 1
Loading compiled-in X.509 certificates
Loaded X.509 cert 'Build time autogenerated kernel key: ecf4bf9cab5cd286fb83bbdfee8b76fad1762609'
zswap: loaded using pool lzo/zbud
Key type trusted registered
Key type encrypted registered
AppArmor: AppArmor sha1 policy hashing enabled
ima: No TPM chip found, activating TPM-bypass!
evm: HMAC attrs: 0x1
Magic number: 9:91:826
rtc_cmos 00:00: setting system clock to 2017-07-06 08:49:32 UTC (1499330972)
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
PM: Hibernation image not present or could not be loaded.
ata2.01: NODEV after polling detection
ata2.00: ATAPI: QEMU DVD-ROM, 2.1.2, max UDMA/100
ata2.00: configured for MWDMA2
scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.1. PQ: 0 ANSI: 5
sr 1:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sr 1:0:0:0: Attached scsi generic sg0 type 5
Freeing unused kernel memory: 1496K (ffffffff81f47000 - ffffffff820bd000)
Write protecting the kernel read-only data: 14336k
Freeing unused kernel memory: 1988K (ffff88000180f000 - ffff880001a00000)
Freeing unused kernel memory: 100K (ffff880001de7000 - ffff880001e00000)
systemd-udevd[142]: starting version 204
input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input4
input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input3
FDC 0 is a S82078B
EXT4-fs (vda1): INFO: recovery required on readonly filesystem
EXT4-fs (vda1): write access will be enabled during recovery
usb 1-1: new full-speed USB device number 2 using uhci_hcd
usb 1-1: New USB device found, idVendor=0627, idProduct=0001
usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5
usb 1-1: Product: QEMU USB Tablet
usb 1-1: Manufacturer: QEMU
usb 1-1: SerialNumber: 42
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input5
hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Pointer [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
tsc: Refined TSC clocksource calibration: 2494.206 MHz
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x23f3d84809a, max_idle_ns: 440795249886 ns
EXT4-fs (vda1): orphan cleanup on readonly fs
EXT4-fs (vda1): 2 orphan inodes deleted
EXT4-fs (vda1): recovery complete
EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
random: init: uninitialized urandom read (12 bytes read, 30 bits of entropy available)
random: mountall: uninitialized urandom read (12 bytes read, 36 bits of entropy available)
EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
random: lsb_release: uninitialized urandom read (24 bytes read, 42 bits of entropy available)
random: cloud-init: uninitialized urandom read (32 bytes read, 60 bits of entropy available)
random: cloud-init: uninitialized urandom read (32 bytes read, 84 bits of entropy available)
systemd-udevd[418]: starting version 204
lp: driver loaded but no devices found
[drm] Initialized drm 1.1.0 20060810
piix4_smbus 0000:00:01.3: SMBus Host Controller at 0x700, revision 0
ppdev: user-space parallel port driver
AVX2 version of gcm_enc/dec engaged.
AES CTR mode by8 optimization enabled
checking generic (fc000000 160000) vs hw (fc000000 2000000)
fb: switching to cirrusdrmfb from EFI VGA
Console: switching to colour dummy device 80x25
[TTM] Zone kernel: Available graphics memory: 4087560 kiB
[TTM] Zone dma32: Available graphics memory: 2097152 kiB
[TTM] Initializing pool allocator
[TTM] Initializing DMA pool allocator
[drm] fb mappable at 0xFC000000
[drm] vram aper at 0xFC000000
[drm] size 33554432
[drm] fb depth is 24
[drm] pitch is 3072
fbcon: cirrusdrmfb (fb0) is primary device
Console: switching to colour frame buffer device 128x48
cirrus 0000:00:02.0: fb0: cirrusdrmfb frame buffer device
[drm] Initialized cirrus 1.0.0 20110418 for 0000:00:02.0 on minor 0
intel_rapl: no valid rapl domains found in package 0
audit: type=1400 audit(1499302181.869:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=513 comm="apparmor_parser"
audit: type=1400 audit(1499302181.869:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=513 comm="apparmor_parser"
audit: type=1400 audit(1499302181.869:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=513 comm="apparmor_parser"
audit: type=1400 audit(1499302181.869:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=514 comm="apparmor_parser"
audit: type=1400 audit(1499302181.869:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=514 comm="apparmor_parser"
audit: type=1400 audit(1499302181.869:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=514 comm="apparmor_parser"
intel_rapl: no valid rapl domains found in package 0
audit: type=1400 audit(1499302181.885:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=542 comm="apparmor_parser"
audit: type=1400 audit(1499302181.885:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=541 comm="apparmor_parser"
intel_rapl: no valid rapl domains found in package 0
intel_rapl: no valid rapl domains found in package 0
random: nonblocking pool is initialized
init: cloud-init-upgrade main process (687) terminated with status 2
init: failsafe main process (778) killed by TERM signal
audit: type=1400 audit(1499302194.037:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=933 comm="apparmor_parser"
audit: type=1400 audit(1499302194.037:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=931 comm="apparmor_parser"
audit: type=1400 audit(1499302194.037:12): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=931 comm="apparmor_parser"
audit: type=1400 audit(1499302194.037:13): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=931 comm="apparmor_parser"
audit: type=1400 audit(1499302194.037:14): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=930 comm="apparmor_parser"
audit: type=1400 audit(1499302194.049:15): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/mysqld" pid=932 comm="apparmor_parser"
audit: type=1400 audit(1499302194.397:16): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=935 comm="apparmor_parser"
audit: type=1400 audit(1499302194.585:17): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/mysqld" pid=1055 comm="apparmor_parser"
aufs 4.x-rcN-20160111
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Bridge firewalling registered
Initializing XFRM netlink socket
aufs au_opts_verify:1597:dockerd[1227]: dirperm1 breaks the protection by the permission bits on the lower branch
init: plymouth-upstart-bridge main process ended, respawning
aufs au_opts_verify:1597:dockerd[1091]: dirperm1 breaks the protection by the permission bits on the lower branch
aufs au_opts_verify:1597:dockerd[1091]: dirperm1 breaks the protection by the permission bits on the lower branch
aufs au_opts_verify:1597:dockerd[825]: dirperm1 breaks the protection by the permission bits on the lower branch
device vethd4b7fe9 entered promiscuous mode
docker0: port 1(vethd4b7fe9) entered forwarding state
docker0: port 1(vethd4b7fe9) entered forwarding state
docker0: port 1(vethd4b7fe9) entered disabled state
cgroup: docker-runc (1955) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
cgroup: "memory" requires setting use_hierarchy to 1 on the root
eth0: renamed from veth1e1327b
docker0: port 1(vethd4b7fe9) entered forwarding state
docker0: port 1(vethd4b7fe9) entered forwarding state
aufs au_opts_verify:1597:dockerd[1436]: dirperm1 breaks the protection by the permission bits on the lower branch
aufs au_opts_verify:1597:dockerd[1436]: dirperm1 breaks the protection by the permission bits on the lower branch
aufs au_opts_verify:1597:dockerd[959]: dirperm1 breaks the protection by the permission bits on the lower branch
docker0: port 1(vethd4b7fe9) entered forwarding state
conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module.
init: kube-scheduler main process (1072) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (1077) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (13828) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (13829) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (13952) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (13953) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (17976) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (17977) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (18239) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (18241) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (22032) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (22121) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (22033) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (22224) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (22233) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (22384) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (22385) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (26231) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (26232) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (26438) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (26445) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (26591) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (26615) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (27494) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (27497) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (27592) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (27602) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (27805) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (27807) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (28649) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (28652) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (28758) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (28768) terminated with status 255
init: kube-controller-manager main process ended, respawning
python (5020): drop_caches: 3
python (5020): drop_caches: 3
python (7790): drop_caches: 3
python (7790): drop_caches: 3
python (10062): drop_caches: 3
python (10062): drop_caches: 3
init: kube-controller-manager main process (28933) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (28930) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (19432) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (19405) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (19530) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (19605) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (22832) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (22833) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (23475) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (23478) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (23583) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (23592) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (23674) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (23675) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (23835) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (23837) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (29202) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (29204) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (29508) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (29483) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (787) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (797) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (881) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (970) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (973) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (1237) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (1241) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (5073) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (5071) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (5180) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (5347) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (5349) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (9168) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (9169) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (9410) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (9412) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (10281) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (10282) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (10590) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (10614) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (11384) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (11387) terminated with status 255
init: kube-controller-manager main process ended, respawning
python (20187): drop_caches: 3
python (20187): drop_caches: 3
python (22474): drop_caches: 3
python (22474): drop_caches: 3
python (24842): drop_caches: 3
python (24842): drop_caches: 3
init: kube-scheduler main process (11647) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (11645) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (5275) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (5272) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (5370) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (9305) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (9306) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (9593) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (9615) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (13472) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (13442) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (13533) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (13754) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (13755) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (18448) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (18449) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (18708) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (18709) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (19540) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (19543) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (19806) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (19808) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (20659) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (20662) terminated with status 255
init: kube-controller-manager main process ended, respawning
python (29138): drop_caches: 3
python (29138): drop_caches: 3
python (31461): drop_caches: 3
python (31461): drop_caches: 3
python (1363): drop_caches: 3
python (1363): drop_caches: 3
init: kube-scheduler main process (20943) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (20968) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (2011) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (2033) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (2112) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (2151) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (2265) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (2264) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (6126) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (6129) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (6422) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (6423) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (10339) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (10338) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (10619) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (10593) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (14580) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (14578) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (14841) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (14860) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (15711) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (15714) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (15895) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (15896) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (27858) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (27860) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (31894) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (31923) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (32076) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (32085) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (32241) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (32242) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (3852) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (3853) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (7858) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (7818) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (7918) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (8018) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (8021) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (8120) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (8140) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (9012) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (9015) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (9156) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (9159) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (9321) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (9323) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (10186) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (10189) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (10409) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (10410) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (10538) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (10563) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (7868) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (7869) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (8160) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (8161) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (11936) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (11939) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (12252) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (12220) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (16085) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (16086) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (16352) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (16349) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (20267) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (20256) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (20368) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (20531) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (20533) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (21426) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (21427) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (21695) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (21693) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (22498) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (22497) terminated with status 255
init: kube-controller-manager main process ended, respawning
python (4609): drop_caches: 3
python (4609): drop_caches: 3
python (6962): drop_caches: 3
python (6962): drop_caches: 3
python (9220): drop_caches: 3
python (9220): drop_caches: 3
init: kube-scheduler main process (22764) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (22777) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (24086) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (24088) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (24216) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (24217) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (28105) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (28106) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (28234) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (28243) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (28326) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (28327) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (28462) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (28485) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (32411) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (32412) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (32499) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (32500) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (32651) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (32652) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (4164) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (4166) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (8558) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (8559) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (8854) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (8855) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (12633) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (12634) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (12880) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (12882) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (19127) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (19126) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (19215) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (19222) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (19317) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (19318) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (19427) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (19428) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (23257) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (23259) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (23510) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (23512) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (27394) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (27393) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (27502) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (27511) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (31442) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (31471) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (31697) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (31695) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (25647) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (25649) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (25909) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (25916) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (29737) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (29738) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (29998) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (29997) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (1351) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (1350) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (1513) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (1639) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (1637) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (5554) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (5552) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (5661) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (5847) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (5871) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (6717) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (6726) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (7003) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (7026) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (7842) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (7851) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (8103) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (8105) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-controller-manager main process (25001) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (24998) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (25260) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (29042) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (29149) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (29043) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (29392) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (29418) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (780) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (781) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (934) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (944) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (4979) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (4980) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (5241) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (5242) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (6134) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (6143) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (6234) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (6243) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (6333) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-scheduler main process (6472) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (6334) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (7384) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (7387) terminated with status 255
init: kube-controller-manager main process ended, respawning
init: kube-scheduler main process (7477) terminated with status 255
init: kube-scheduler main process ended, respawning
init: kube-controller-manager main process (7478) terminated with status 255
init: kube-controller-manager main process ended, respawning